home *** CD-ROM | disk | FTP | other *** search
- Path: ccnet.com!usenet
- From: slider
- Newsgroups: comp.sys.amiga.hardware
- Subject: Re: SCSI question #4376:-.long boot answer
- Date: 20 Jan 1996 21:13:52 GMT
- Organization: Jay Miner........Father of great things and a true engineering visionary...he is sorely missed around the world
- Message-ID: <4drlug$7qd@ccnet2.ccnet.com>
- References: <4dlrp7$jad@news.sdd.hp.com>
- NNTP-Posting-Host: h108-14-206.ccnet.com
- X-Newsreader: SPRY News 3.03 (SPRY, Inc.)
-
- -> Jeff Grimmett <jgrimm@sdd.hp.com> writes:
- -> rhays@ansel.intersource.com (Rob Hays) wrote:
- -> >I have an A3000 to which I have added a Syquest 105 drive internally in
- -> >the spot intended for the second floppy drive. When I boot, if there
- -> >is no cartridge in the Syquest, the system waits approx 30 seconds before
- -> >booting from the boot partition of the internal hard drive.
- ->
- -> No matter where on the SCSI chain the Syquest is, (or any other removable
- -> media hard drive), the system will wait for it to make up its mind and
- -> report whether it has a disk or not. The exact same thing happens with
- -> my Zip and my Insite floptical. You either get used to it, or you keep a
- -> disk in there. If you have it mounted in the internal drive bay, I
- -> suggest you keep a disk in it anyway -- you don't want to suck dust in
- -> through that drive...
- ->
- ->
- ->
- ->>>>
- The answer everyone has been waiting for it looks like!! Heehee
- I went over this with a fellow many many moons ago but here goes again
- When using a commodore SCSI controller or commodore scsi.device
- controller, when you prep and format your scsi devices under this controller
- it saves the device parameters to a file so it can recall what exactly the device
- was set for when you formatted it. By default (unless you change it) HDTOOLBOX
- sets these prepped/formatted devices to automount on startup. Problem with
- removable media is that if there is no disk to actually automount on startup the scsi.device
- waits for the standard (loooooooooong) timeout before forgetting the device and allowing
- your system to boot. You can change this timeout using the shareware program (or is it freeware?)
- called setbatt or any program that allows you to change the battery backed ram (of course in an A3000 only)
- but the 2091 i'm not sure of or the 4091 they might be hard coded and not have a battery backed ram
- holding the scsi information. But you can change the timeout to be short which will allow the scsi.device
- to timeout quickly on removable media devices that have no disk inserted on boot if that device was
- originally defined as "mount at startup" in the HDTOOLBOX programs parameter file for it. Similar
- problems occur on GVP scsi as well as many others if they follow commodores RDB standard..Why exactly
- I really don't know....guess they all liked the very loooooong timeout setting! :)
- whew!!!!!
- Ok there ya go another mystery uncovered.............
-
- laterzzzzzz.
- James Vigliotti
- slider@ccnet.com
- P.S. why commodore chose such a loooooooong timeout for scsi devices is beyond me.
- "If the sucka hasn't spoke up in 20seconds it ain't gonna talk period!!!"
-
-